Foreign function interface
A foreign function interface (or FFI) is a mechanism by which a program written in one programming language can call routines or make use of services written in another. The term comes from the specification for Common Lisp, which explicitly refers to the language features for inter-language calls as such; the term is also used officially by the Haskell programming language. Other languages use other terminology (the Ada programming language talks about "language bindings", while Java refers to its FFI as the Java Native Interface, or JNI). Foreign function interface has become generic terminology for mechanisms which provide such services.
Despite the name, FFIs are not necessarily restricted to function calls; many FFIs permit method calls on objects; and some even permit migration of non-trivial datatypes and/or objects across the language boundary.
The term foreign function interface is generally not used to describe multi-lingual runtimes such as the Microsoft Common Language Runtime, where a common "substrate" is provided which enables any CLR-compliant language to use services defined in any other. (However, in this case the CLR does include an FFI, P/Invoke, to call outside the runtime.) In addition, many distributed computing architectures such as the Java remote method invocation (RMI), RPC, CORBA, SOAP and D-Bus permit different services to be written in different languages; such architectures are generally not considered FFIs.
In most cases, a FFI is defined by a "higher-level" language, so that it may employ services defined and implemented in a lower level language, typically a systems language like C or C++. This is typically done to either access OS services in the language in which the OS' API is defined, or for performance considerations.
Many FFIs also provide the means for the called language to invoke services in the host language as well.
Operation of an FFI
The primary function of a FFI is to mate the semantics and calling conventions of one programming language (the host language, or the language which defines the FFI), with the semantics and conventions of another (the guest language). This process must also take into consideration the runtime environments and/or application binary interfaces of both. This can be done in several ways:
- Requiring that guest-language functions which are to be host-language callable be specified or implemented in a particular way; often using a compatibility library of some sort.
- Use of a tool to automatically "wrap" guest-language functions with appropriate glue code, which performs any necessary translation.
- Use of wrapper libraries
- Restricting the set of host language capabilities which can be used cross-language. For example, C++ functions called from C may not (in general) include reference parameters or throw exceptions.
FFIs may be complicated by the following considerations:
- If one language supports garbage collection (GC) and the other does not; care must be taken that the non-GC language code doesn't do something to cause the GC to fail. In JNI, for example, C code which "holds on to" object references passed from Java must "register" this fact with the Java runtime; otherwise the referred-to objects may be garbage-collected if no more valid references to the object(s) exist within the Java environment. (The C code must likewise release such references manually when the corresponding object is no longer needed).
- Complicated or non-trivial objects or datatype may be difficult to map from one environment to another.
- It may not be possible for both languages to maintain references to the same instance of a mutable object, due to the mapping issue above.
- One or both languages may be running on a virtual machine (including different VMs).
- Cross language inheritance or other forms of type or object composition may be especially difficult.
Examples
Examples of FFIs include:
- Ada language bindings, allowing not only to call foreign functions but also to export its functions and methods to be called from non-Ada code.[1]
- C++ has a trivial FFI with C, as the languages share a significant common subset. The primary effect of the extern "C" declaration in C++ is to disable name mangling.
- JNI, which provides an interface between Java and C/C++, the preferred systems language on most systems where Java is deployed. JNA provide an interface with native libraries without having to write Glue code.
- CNI, alternative to JNI used in the GNU compiler environment.
- The FFIs of Common Lisp and Haskell
- The major dynamic languages, such as Python, Perl, Tcl, and Ruby, all provide easy access to native code written in C/C++ (or any other language obeying C/C++ calling conventions).
- Python additionally provides the Ctypes module [2], which can load C functions from shared libraries/DLLs on-the-fly and translate simple data types automatically between Python and C semantics. For example:
import ctypes
libc = ctypes.CDLL( '/lib/libc.so.6' ) # under Linux/Unix
t = libc.time(None) # equivalent C code: t = time(NULL)
print t
- P/Invoke, which provides an interface between the Microsoft Common Language Runtime and native code.
- Racket has a native FFI based heavily on macros that enables importing arbitrary shared libraries dynamically.[3][1]
- Factor has FFI for C[4], Fortran[5], Objective-C[6], and Windows COM[7]; all of these enable importing and calling arbitrary shared libraries dynamically.
- Visual Basic has a declarative syntax that allows it to call non-unicode C functions.
- One of the bases of the Component Object Model is a common interface format, which natively uses the same types as Visual Basic for strings and arrays.
- GWT, in which Java is compiled to JavaScript, has a FFI called JSNI which allows Java source to call arbitrary JavaScript functions, and for JavaScript to call back into Java.
- LuaJIT, a just-in-time implementation of Lua, does have a FFI that allows "calling external C functions and using C data structures from pure Lua code"[8].
In addition, many FFIs can be generated automatically: for example, SWIG. However, in the case of an Extension language a semantic inversion of the relationship of guest and host can occur, when a smaller body of extension language is the guest invoking services in the larger body of host language, such as writing a small plugin [9] for GIMP [10].
See also
References
- ^ http://repository.readscheme.org/ftp/papers/sw2004/barzilay.pdf
External links